same here since monterey beta 5

I reported this with the feedback assistant ( FB9704765 and FB9704771 ) as xcode and monterey error on 15 October. The Resolution ist still open.

There is still no solution for MacOS 12.1 Beta (21C5031d) ( Xcode 13.1 and Xcode 13.2 Beta), the feedback reports are still open and no similar other feedback reports. (even if both are the same) I think nobody take a look about it and Xcode server is abandoned for Xcode cloud which is not available for anyone yet.

reinstall monterey and it is still broken

https://feedbackassistant.apple.com/feedback/9704771 ( XCode 13 Server installation failed with libre ssl certificate error ) https://feedbackassistant.apple.com/feedback/9704765 Recent Similar Reports: None Resolution: Open What about FB9732898 FB9785825 are them still with no recent similar reports and open too?

M1 Mac Mini & MB Pro M1 Max and no Problems. I never migrate machines or restore Backups on a fresh install because it is not a fresh install ;)

Same here, Xcode Server is not starting and with 14.2 all my bots can't checkout the git repository. New Git Repositories are working the old projects not. Apple should be aware that the Xcode server is used productively, right? It's probably only a matter of time before it's completely removed.

I have the same problem, xcodebuild permanently set the old model, even if I explicitly change that manually in .xccurrentVersion and start the build.

I have solved it temporarily by revoking the write permissions to the directory CoreData.xcdatamodeld (chmod -w ).

@LZBLT Unfortunately, I can't say exactly how long we've had this error. But even in a new test project there is the same behavior.

@LZBLT But it seems to work if I write the version number at the beginning of the model. Xcode seems to simply take the last sorted file from the package / directory. but I don't know what effect this has on the live app and the existing database. We actually have a version number but I don't know if the name of the model is used. Old Name was eg: BaseDataBaseV1 AddedNewEntityV2 NewEntityAdditionV3 now: V1BaseDataBase V2AddedNewEntity V3NewEntityAddition I also don't think that the file is ever read for configuration and is simply overwritten directly when the project is open and then works with the new (wrong) values.

if you set an own identifier there should be no problem with the hash from the old model if you rename the model files.